There Is Still No Silver Bullet

No silver bullet: De-identification still doesn't work.docx

Paul Ohm’s 2009 article “Broken Promises of Privacy” spurred a debate in legal and policy circles on the appropriate response to computer science research on re-identification.1 In this debate, the empirical research has often been misunderstood or misrepresented. A new report by Ann Cavoukian and Daniel Castro is full of such inaccuracies, despite its claims of “setting the record straight.”2

The Inevitable Pain of Software Development: Why There Is No Silver Bullet

A variety of programming accidents, i.e., models, methods, artifacts, and tools, are examined to determine that each has a step that programmers find very painful. Consequently, they habitually avoid or postpone the step. This pain is generally where the programming accident meets requirements, the essence of software, and their relentless volatility. Hence, there is no silver bullet.

There is no silver bullet: The value of diversification in planning invasive species surveillance

a Natural Resources Canada, Canadian Forest Service, Great Lakes Forestry Centre, 1219 Queen Street East, Sault Ste. Marie, ON P6A 2E5, Canada b USDA Forest Service, Southern Research Station, Eastern Forest Environmental Threat Assessment Center, 3041 Cornwallis Road, Research Triangle Park, NC 27709, USA c USDA Forest Service, Southern Research Station, 3041 Cornwallis Road, Research Triangle...

E-Commerce Security: No Silver Bullet

No Silver Bullet – The Evolutionary Model

This paper’s objective is to present an evolutionary model that better explains the behavior of the gap between software engineering (SE) essence difficulties and SE capabilities, and adds an evolutionary dimension to Brooks’s approach regarding the gap. In his 1987 landmark paper, Brooks argues that software projects incorporate inherent essence-conceptual difficulties that are unchanging and ...